Global Variables
Boomi's Global Variables feature is rolling out in waves to eligible accounts. You can request access to get the latest functionality.
Global variables provide a unified approach for configuration management, allowing you to effectively centralize process variable overrides.
Global variables vs environment extensions
Environment extensions are used to override key fields in components, such as maps and cross-reference tables, and are managed and configured in Runtime Management for each environment. Extensions are enabled on a process-by-process basis and require you to set a value for each process in each environment.
Global variables also override key fields in components, however you create them on a centralized page and they apply to your entire account. Variables can be referenced in multiple processes and components and you manage their values from one location. Global variables can currently be used in any text field and encrypted text field, such as a password or token field, in certain components. The following table outlines the components that support global variables:
| Integration Component | Supported by Extensions | Supported by Variables |
|---|---|---|
| Connection settings |  | |
| Trading Partner settings | | |
| Operation settings | | |
| Maps | |  |
| Cross-reference tables | | |
| Certificates | | |
| Integration Packs | | |
| Field Encryption | (Limited) | |
| Process properties | | |
Additional capabilities will be added for global variables in future releases.
Required privileges
To manage and view global variables, you must have the following privileges:
| Privilege | Description |
|---|---|
| Define Global Variable | Create and edit global variables, including its name, description, and initial value. |
| Assign Global Variable Value | Assign environment-specific values to existing global variables. You must also have the Environment Management privilege. |
| View Global Variables Value | View global variable definitions and their assigned values across environments. |
Limitations
Global variables currently have the following limitations:
-
Test Mode - Because Test Mode currently executes the literal value typed into the component's field, it will not use the value assigned to the global variable in the environment. To test a specific value, you must temporarily replace the variable notation (
$V{VARIABLE_NAME}) with the desired value in the component field, then revert the change before deployment. -
Test Connection - The Test Connection feature on Connection components is not compatible with global variables. To test the connection, you must temporarily replace the variable notation (
$V{VARIABLE_NAME}) with the desired value in the component field. Be sure to revert back to the global variable reference after testing the connection. -
Import Operations - The Import function in Operation components is not compatible if you used global variables in the associated Connection component. To import, temporarily replace the variable notation (
$V{VARIABLE_NAME}) with a literal value in the component field. Perform the import, then revert back to the global variable reference in the field. -
Listeners do not currently support global variables.
Example use case
An Integration user with global variables privileges can create variables for the account. Then, multiple developers in the account can configure and use the variables in both Production and Test environments. This ensures that important values, such as Connection settings or encrypted passwords, are consistent in all processes created in the account.
